se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Fall/Spring |
Prerequisites |
| ||||||||
Course Language | |||||||||
Course Type | Elective | ||||||||
Course Level | - | ||||||||
Mode of Delivery | - | ||||||||
Teaching Methods and Techniques of the Course | Group WorkProblem Solving | ||||||||
Course Coordinator | - | ||||||||
Course Lecturer(s) | |||||||||
Assistant(s) | - |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | X |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Fundamental Concepts | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch1.1, pp. 1-14 |
2 | Cryptographic Concepts | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch1.2, pp 19-31 |
3 | Symmetric Cryptography | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch2.1 pp. 53-68 |
4 | Publi-Key Cryptography | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch2.2 pp. 72-81 |
5 | Cryptographic Hash Functions | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch2.3-Ch2.4 pp. 83-88 |
6 | Digital Signatures | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch2.4-Ch2.5, pp. 89-97 |
7 | Operating Systems Security | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch3 pp. 111-157 |
8 | Malicious Software | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch4 pp. 167-208 |
9 | MIDTERM EXAM | |
10 | Network Security | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch5.1-Ch5.2 pp. 215-227 |
11 | Network Security | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch5.3-Ch5. 6 pp. 230-256 |
12 | Network Services & Security | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch6 pp. 261-310 |
13 | Browser Security | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch7 pp. 319-372 |
14 | Security Models & Practice | Introduction to Computer Security - M. T. Goodrich and R. Tamassia – Ch9 pp. 435-474 |
15 | Project Presentations | |
16 | Review of the Semester |
Course Notes/Textbooks | Cryptography and Network Security Fourth Ed., William Stallings,© 2006 | Pearson Prentice Hall | ISBN: 0131873184 |
Suggested Readings/Materials |
Semester Activities | Number | Weigthing |
Participation | 16 | 10 |
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | ||
Portfolio | ||
Homework / Assignments | ||
Presentation / Jury | ||
Project | 2 | 60 |
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 30 |
Final Exam | ||
Total |
Weighting of Semester Activities on the Final Grade | 3 | 60 |
Weighting of End-of-Semester Activities on the Final Grade | 1 | 40 |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 1 | 16 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | 2 | |
Study Hours Out of Class | 10 | 2 | |
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | |||
Presentation / Jury | |||
Project | 2 | 27 | |
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 28 | |
Final Exams | |||
Total | 150 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | |||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | |||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | |||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | |||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | |||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | |||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | |||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | |||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest